home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1993
/
Internet Info CD-ROM (Walnut Creek) (1993).iso
/
info
/
us-domain
< prev
next >
Wrap
Text File
|
1993-05-13
|
27KB
|
724 lines
[ Please direct questions about the US domain or name service for US
domains to the US Domain Registrar (us-domain-request@ISI.EDU). If
you are a UUNET subscriber and wish to use UUNET as your MX, please
contact us so we can configure things -- postmaster@uunet.uu.net ]
The US Domain [5/93]
=============
The US Domain is an official top-level domain in the DNS of the
Internet community. It is registered with the Internic. The domain
administrators are Jon Postel and Ann Westine Cooper at the
Information Sciences Institute of the University of Southern
California (USC-ISI).
US is the ISO-3166 2-letter country code for the United States and
thus the US Domain is established as a top-level domain and registered
with the NIC the same way other country domains are.
Membership:
Any computer in the United States may be registered in the US domain.
In the past, the computers registered in the US Domain were primarily
owned by small companies or individuals with computers at home.
However, the US Domain has grown and currently registers hosts in
federal government agencies, state government agencies, K12 schools,
community colleges, technical/vocational schools, private schools,
libraries, city and county government agencies, as well as in
businesses and homes.
Registration Requirements:
Anyone requesting to register a host in the US Domain is sent a copy
of the US Domain policy and procedure and must fill out a US Domain
questionnaire (also called a template).
The US Domain template, is similar to the Internic Domain template,
but it is not the same. To request a copy of the US Domain
questionnaire, send a message to the US Domain registrar
(us-domain@isi.edu).
If you are registering a name in a delegated zone, please register
with the contact for that zone. You can ftp the file from
venera.isi.edu, via anonymous ftp, in-notes/delegated-domains.txt.
Delegation:
Many branches of the US Domain are delegated, for example, cities, or
K12 in a state. There must be a knowledgeable and competent technical
contact, familiar with the Internet Domain Name System. This
requirement is easily satisified if the technical contact already runs
some other nameservers.
Organizations requesting delegations must provide at least two
independent DNS name servers in physically separate locations on the
Internet. The subdomain must accept all applicants on an equal basis.
The subdomain must provide timely processing of requests. To do
this it is helpful to have several individuals knowledgeable about the
procedures so that the operations are not delayed.
Typical delegations are localities (cities or counties), companies
within cities, k12 schools, community colleges, libraries,
state and federal government agencies.
WHOIS Database:
Only the third level delegated portions of the US Domain will be
entered in the Internic WHOIS database. The data from the information
you supplied on your application will be sent to the Internic registry
automatically.
Servers:
The US domain is currently supported by seven name servers:
VENERA.ISI.EDU, NS.ISI.EDU, RS.INTERNIC.NET, NS.CSL.SRI.COM,
NS.UU.NET, ADM.BRL.MIL and EXCALIBUR.USC.EDU.
Cost:
Currently, there is no cost for registering a host in the US domain.
UUCP Hosts:
Many applicants have hosts in the UUCP world. Some are one hop away,
some two and three hops away from their "Internet Forwarder", this is
ok. What is important is getting an Internet host to be your
forwarder. If you do not already have an Internet forwarder, there
are several businesses that provide this service for a fee, (see RFC
1359 - Connecting to the Internet What Connecting Institutions Should
Anticipate, ACM SIGUCCS, August 1992). Sometimes local colleges in
your area are already on the Internet and may be willing to act as an
Internet Forwarder. You would need to work this out with the systems
administrator. Only hosts on the Internet can act as forwarding hosts.
It is important that you register with an Internet forwarding host.
When registering a destination host in the US domain with an MX
record, the requester is responsible for also registering the
destination host with the administrator of the forwarding host. This
is necessary because when messages for your host arrive at the
Internet host it will need to know where to forward them. MX records
are necessary.
For example, when a message is sent to "Susan@ALPHA.CLUB.CHI.IL.US" it
will be routed to the Internet host "CS.CHICAGO-U.EDU" as directed
by the MX record. The host "CS.CHICAGO-U.EDU" must know some way of
delivering the message to the host "ALPHA.CLUB.CHI.IL.US" (uucp, slip,
whatever). So the destination host (ALPHA.CLUB.CHI.IL.US) must be
known to (registered with) the forwarding host (CS.CHICAGO-U.EDU), as
well as being registered in the US domain DNS database.
The Internet US Domain registration is not affiliated with the
registration of UUCP Map entries. The UUCP map entry does not provide
us with sufficient information.
Wild Cards:
Wildcard records are allowed in our zone files under the
organizational subdomain but no wildcard records are allowed under the
"City" or "State" domain.
The wildcard records are of the form "*.<anydomain>". The wildcards
potentially apply to descendents of <anydomain>, but not to
<anydomain> itself. For example: "*.dwp.la.ca.us.
dwp.la.ca.us MX 10 ELROY.JPL.NASA.GOV
*.dwp.la.ca.us MX 10 ELROY.JPL.NASA.GOV
The wildcard record *.DWP.LA.CA.US would cause an MX query for any
domain name ending in DWP.LA.CA.US to return an MX RR pointing at
ELROY.JPL.NASA.GOV. The entry without the "*" is needed so the host
dwp can be found.
Naming Structure:
The US domain hierarchy is based on political geography, that is, the
US domain is subdivided into states, then locality (i.e., city or
county) then organization or computer name and so on. The state codes
are those assigned by the US Postal Service.
Locality Names:
Within the state namespace there are "locality" names, some
may be cities, some may be counties, some may be local names, but not
incorporated entities.
Registered names under "locality" would be like:
<hostname>.CI.<locality>.<state>.US ==> city gov't agency
<hostname>.CO.<locality>.<state>.US, ==> county gov't agency
<hostname>.<locality>.<state>.US ==> businesses
In the cases where the locality name is a county, there is a branch
under the locality name, called "county" or "CO", that is used by the
county government. Businesses are registered directly under the
locality name.
Under the city locality namespace there is a "CITY" or "CI" branch for
city government agencies. As usual, businesses and private schools
may register directly under the city name.
In the case where there is both a county and a city with the same
locality name there is no problem, since the names will be unique with
the "CO" or "CI" key word. In our area the county has a fire
department and the city has its own fire department.
Cities may be named (designated) by their full name (spelled out with
hyphens replacing spaces (e.g., Los-Angeles or New-York)), or by a
city code. The first choice is the full city name, the second choice
is the city codes from Western Union's "City Mnemonics" list, and a
third choice is a code for your city that you choose. However, it is
very desirable that all users in the same city use the same designator
for the city. That is, any particular locality should have just one
DNS name.
K12 Schools Under US Domain:
Many schools are now connecting to the Internet and registering in the
Internet Domain Name System. A decision has been made by the Internet
Assigned Numbers Authority (after consultation with the new INTERNIC
Internet Registry and the FNC) to direct these school registrations to
the US domain using the naming structure described in RFC 1386.
There are two reasons for registering schools in the US Domain.
(1) uniqueness of names, and (2) management of the database. For
both these reasons it is necessary to introduce structure into names.
Structure provides a basis for making common names unique in context,
and for dividing the management responsibility.
The US Domain has a framework established and has registered many
schools already in this structured scheme. The general form is:
<school>.<district>.K12.<state>.US.
Generally school names are unique within a district, and this provides
two points at which to delegate a branch of the database to distinct
administrators -- the K12 administrator for each state, and the
district administrator for each district within a state.
These names are generally longer than the current apparent
alternative in the EDU domain, but that cannot last long without a
significant number of schools finding that their "obviously correct"
name has already been used by some other school.
Private Schools
To accommodate both public and private schools, in each state's K12
branch, we've added an artificial district called private or "PVT".
This gives a private school the option of registering like a business
or in the PVT.K12.<state-code>.US branch.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
"CI" - This branch is used for city government agencies and is
a subdomain under the "locality" name (like Los Angeles).
For example: Fire-Dept.CI.Los-Angeles.CA.US.
"CO" - This branch is used for city government agencies and is
a subdomain under the "locality" name (like Los Angeles).
For example: Fire-Dept.CO.Los-Angeles.CA.US.
"K12" - This branch may be used for public school districts. A
special name "PVT" can be used in the place of a school district name
for private schools. For example: <school>.<district>.K12.<state>.US and
<school>.PVT.K12.<state>.US.
"CC" COMMUNITY COLLEGES - This branch was established for all state
wide community colleges. For example <school>.CC.<state>.US.
"TEC" TECHNICAL AND VOCATIONAL SCHOOLS - The branch "TEC" was
established for technical and vocational schools and colleges. For
example: <school>.TEC.<state>.US.
"GEN" is for general independent entities, that is, organizations that
don't really fit anywhere else (such as statewide associations, clubs,
and "domain parks"). For example: Comp-Club.GEN.CA.US.
"LIB" LIBRARIES (STATE, REGIONAL, CITY, COUNTY) - This branch may be
used for libraries only. For example: <lib-name>.LIB.<state>.US
"STATE" - This branch may be used for state government agencies.
For example. <org-name>.STATE.<state>.US.
"FED" - This branch may be used for agencies of the federal
government. For example: <org-name>.FED.US.
"DNI" DISTRIBUTED NATIONAL INSTITUTES - The "DNI" branch was created
directly under the top level .US. This branch is to be used for
distributed national institutes; organizations that span state,
regional, and other organizational boundaries; that are national in
scope, and have distributed facilities. For example
<org-name>.DNI.US.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
VIEW OF SECOND LEVEL DOMAINS UNDER US
+-------+
| US |
+-------+
|
+----------------------------------+
| | | | |
+-----+ +-----+ +-----+ +-----+ +-----+
| FED | | DNI | | TX | | SD | | CA |
+-----+ +-----+ +-----+ +-----+ +-----+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SCHOOL AND LIBRARY VIEW
+-----+
| CA |
+-----+
|
+------------------------------------------------+
| | | | |
+-----+ +-----+ +-----+ +-------------+ +-----+
| K12 | | CC | | TEC | | LOS ANGELES | | LIB |
+-----+ +-----+ +-----+ +-------------+ +-----+
/ \ /|\ /|\ /|\ /|\
+--------+ +---+ +---+ +--------+ +----------+ +------+
|sch dist| |PVT| |SJC| |WM TRADE| |pvt school| |MALIBU|
+--------+ +---+ +---+ +--------+ +----------+ +------+
/|\ /|\
+--------+ +--------+
|sch name| |sch name|
+--------+ +--------+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
VIEW OF STATE, REGIONAL, and GENERAL AGENCIES
+-----+
| CA |
+-----+
|
+------------------------+
| | |
+-------+ +--------+ +-----+
| STATE | |DISTRICT| | GEN |
+-------+ +--------+ +-----+
/|\ /|\ /|\
+--------+ +------+ +---------+
|CALTRANS| |SCAQMD| |domain pk|
---------+ +------+ +---------+
|
+--------+
|TCEW100E|
+--------+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
VIEW OF LOCALITY
+-----+
| CA |
+-----+
|
+-----------------------------------+
| |
+-------------------------+ +----------------+
| LOS ANGELES | | SANTA MONICA |
+-------------------------+ +----------------+
/ | | /|\ | /|\
/ | | | | |
+---+ +--+ +--+ +-----------+ +--+ +---+
|bus| |CI| |CO| | pvt school| |CI| |bus|
+---+ +--+ +--+ +-----------+ +--+ +---+
/\ | \ |
/ \ | \ +------------+
/ \ | \ |HARBOR GUARD|
/ \ | \ +------------+
+----+ +-----+ +-----+ +----+
|FIRE| |ADMIN| |PARKS| |FIRE|
+----+ +-----+ +-----+ +----+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Examples:
=========
Geo-Petrellis.Culver-City.CA.US <== a resturant
IBM.Armonk.NY.US <== a business
Camp-Curry.Yosemite.CA.US <== a business
Yosemite.NPS.Interior.FED.US <== a federal agency
Senate.FED.US <== US Senate
DOD.FED.US <== US Defense Dept.
DOT.FED.US <== US Transportation Dept.
MPLS.FRB.FED.US <== the Minneapolis branch
of the Federal Reserve Bank
MetaCenter.DNI.US <== a distributed Nat'l Inst.
Senate.STATE.MN.US <== state Senate
House.STATE.MN.US <== state House of Reps
Assembly.STATE.CA.US <== state Assembly
MDH.STATE.MN.US <== state Health Dept.
DOT.STATE.MN.US <== state Transportation Dept.
CALTRANS.STATE.CA.US <== state Transportation Dept.
DMV.STATE.CA.US <== state Motor Vehicles Dept.
Culver-City.DMV.STATE.CA.US <== a local office of DMV
Police.CI.Culver-City.CA.US <== a city department
Fire-Dept.CI.Los-Angeles.CA.US <== a city department
Fire-Dept.CO.Los-Angeles.CA.US <== a county department
MDR.Library.CO.Los-Angeles.CA.US <== a county department
Main.Library.CI.Los-Angeles.CA.US <== a city department
Huntington.LIB.CA.US <== a private library
SMCC.Santa-Monica.CC.CA.US <== a public community college
Trade-Tech.Los-Angeles.CC.CA.US <== a public community college
Valley.Los-Angeles.CC.CA.US <== a public community college
Hamilton.High.LA-Unified.K12.CA.US <== a public school
Sherman-Oaks.Elem.LA-Unified.K12.CA.US <== a public school
John-Muir.Middle.Santa-Monica.K12.CA.US <== a public school
St-Monica.High.Santa-Monica.CA.US <== a private school
Crossroads-School.Santa-Monica.CA.US <== a private school
Mary-Ellens-Montessori-School.LA.CA.US <== a private school
Progress-Learning-Center.PVT.K12.CA.US <== a private school
Brick-and-Basket-Institute.TEC.CA.US <== a technical college
Bunker-Hill.DISTRICT.Los-Angeles.CA.US <== a local district
SCAQMD.DISTRICT.CA.US <== a regional district
Berkeley.UC.STATE.CA.US <== "CAL"
Los-Angeles.UC.STATE.CA.US <== UCLA
Irvine.UC.STATE.CA.US <== UC Irvine
Northridge.CSU.STATE.CA.US <== CSUN
Leland-Stanford-Jr-University.Stanford.CA.US <== a private school
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
US DOMAIN QUESTIONNAIRE FOR HOST ENTRY
May 1993
To register a host in the US domain, the US Domain Template must be
sent to the US Domain Registrar (US-Domain@ISI.EDU). The first few
pages explain each question on the attached template. Questions may
be sent by electronic mail to the above address, or by phone to Ann
Cooper, USC/Information Sciences Institute, (310) 822-1511.
EXPLANATION OF QUESTIONS ON US DOMAIN TEMPLATE
(1) Please specify whether this is a new application, modification to
an existing registration, or deletion.
(2) The name of the host. This is the name that will be used in tables
and lists associating the domain with the domain server addresses.
See RFC 1386 - The US Domain for more details.
<host>.<city/locality>.<state>.US. = city/locality based names
<school>.<district>.K12.<state>.US. = kindegarten thru 12th grade
<school>.PVT.K12.<state>.US. = private K thru 12th grade
school>.<locality>.<state>.US. = PVT sch opt: locality names
<school>.CC.<state>.US. = community colleges
<school>.TEC.<state>.US. = technical or vocational schools
<lib-name>.LIB.<state>.US. = libraries
<org-name>.STATE.<state>.US. = state government agencies
<org-name>.FED.US. = federal government agencies
<org-name>.DNI.US. = distributed national institutes
<org>.GEN.<state>.US. = statewide assoc,clubs,domain parks
For example: networthy.santa-clara.ca.us.
(3) The name and address of the organization establishing the domain.
(4) The date you expect the domain to be fully operational.
(5) The name of the administrative head, zone and or technical contact
of the organization, including title, mailing address, phone
number, organization, and network mailbox. The administrator is
the contact point for administrative and policy questions about the
domain. In the case of a research project, this should be the
principal investigator.
We need both the Administrative and the Technical/Zone contacts of
a domain and we MUST have a network mailbox for each. If you have
a NIC handle (a unique NIC database identifier) please enter it.
(If you don't know what a NIC handle is leave it blank).
(6) The name of the technical and zone contacts. The technical and
zone contacts handle problems concerning the domain or zone, as
well as for updating information about the domain or zone.
(7) Domains must provide at least two independent servers that provide
the domain service for translating names to addresses for hosts in
this domain. If you are applying for a domain and a network number
assignment simultaneously and a host on your proposed network will
be used as a server for the domain, you must wait until you receive
your network number assigment and have given the server(s) a
netaddress before sending in the domain application.
Establishing the servers in physically separate locations and on
different PSNs and/or networks is strongly recommended.
Note: For those applicants not able to run nameservers, or for
non-Internet hosts, the Name Server information is not
applicable. (See questions 10 and 11).
(8)* The Secondary Server Informaion.
(9) Please describe your organization briefly.
For example: Our corporation is a consulting organization of people
working with UNIX and the C language in an electronic networking
environment. It sponsors two technical conferences annually and
distributes a bimonthly newsletter.
====================================================================
QUESTIONS FOR NON-DELEGATED HOSTS OR NON-IP HOSTS (such as UUCP).
Not everyone is going to be able to run two nameservers for their
hosts, but might need Internet Forwarders to do this for them.
Many applicants have hosts in the UUCP world. Some are one hop away,
some two and three hops away from their "Internet Forwarder", this is
ok. What is important is getting an Internet host to be your
forwarder. If you do not already have an Internet forwarder, there
are several businesses that provide this service for a fee, (see
RFC 1359 - Connecting to the Internet What Connecting Institutions
Should Anticipate, ACM SIGUCCS, August 1992). Sometimes local colleges
in your area are already on the Internet and may be willing to act
as an Internet Forwarder. You would need to work this out with the
systems administrator. We cannot make these arrangements for you.
(10) How does your machine communicate with the Internet?
Through IP, UUCP, other?
(10a) What is the name of your forwarding host?
For example: The host "Networthy.Santa-Clara.CA.US" uses
UUCP to connect to "RELAY.ISI.EDU" which is an Internet
host. (i.e., RELAY.ISI.EDU is the forwarding host).
(10b) What is the name of your contact person at fowarding host?
The Administrator of RELAY.ISI.EDU must agree to be the
forwarding host for Networthy.Santa-Clara.CA.US, and the
forwarding host must know a delivery method and route to
Networthy. No double MXing.
(10c) What is the mailbox of your contact?
What is the mailbox of the administrator of the forwarding
host.
Example: Contact Name......: John Smith
Contact Email.....: js@RELAY.ISI.EDU
(11) What Domain Name System (DNS) Resource Records (RR) and values are
to be entered.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Example: RRs for an INTERNET hosts.
FQ DOMAIN NAME......: Networthy.Santa-Clara.CA.US.
IP ADDRESS..........: A 128.9.3.123 (required)
HARDWARE............: SUN-3/11O
OPERATING SYS.......: UNIX
WKS.................: 128.9.3.123. UDP (echo tftp) TCP (ftp)
MX (mail exchanger).: 10 RELAY.ISI.EDU.
Example: RRs for a NON-INTERNET host.
FQ DOMAIN NAME......: Yacht-Club.MDR.CA.US.
HARDWARE............: SUN-3/11O (optional)
OPERATING SYS.......: UNIX (optional)
MX..................: 10 RELAY.ISI.EDU. (required)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
It is your responsibility to see that an IN-ADDR pointer record is
entered in the DNS database. (For internet hosts only.) Contact the
administrator of the IP network your host is on to have this done. The
US Domain administration does not administer the network and cannot make
these entries in the DNS database.
PLEASE ALLOW AT LEAST 8 WORKING DAYS FOR PROCESSING THIS APPLICATION
RECOMMENDED READING
Cooper, Postel, "The US Domain". Marina del Rey, CA: University of
Southern California, Information Sciences Inst.; 1992 December; RFC
1386. 31 p. (RS.INTERNIC.NET RFC:RFC1386.TXT).
Albitz, P., C. Liu, "DNS and Bind" Help for UNIX System
Administrators, O'Reilly and Associates, Inc., October 1992.
Stahl, M.K. Domain Administrators Guide. Menlo Park, CA: SRI
International, DDN Network Information Center; 1987 November; RFC
1032. 14 p. (RS.INTERNIC.NET RFC:RFC1032.TXT).
Lottor, M. Domain Administrators Operations Guide. Menlo Park, CA:
SRI International, DDN Network Information Center; 1987 November;
RFC 1033. 22 p. (RS.INTERNIC.NET RFC:RFC1033.TXT).
Mockapetris, P. Domain Names - Concepts and Facilities. Marina del
Rey, CA: University of Southern California, Information Sciences
Inst.; 1987 November; RFC 1034. 55 p. (RS.INTERNIC.NET RFC:RFC1034.TXT).
Updated-by: RFC 1101 Obsoletes: RFC 973; RFC 882; RFC 883.
Mockapetris, P. Domain Names - Implementation and Specification.
Sciences Inst.; 1987 November; RFC 1035. 55 p. (RS.INTERNIC.NET
RFC:RFC1035.TXT). Updated-by: RFC 1101 Obsoletes: RFC 973;
RFC 882; RFC 883.
ACM SIGUCCS (Networking Taskforce), "Connecting to the Internet -
What Connecting Institutions Should Anticipate", RFC 1359,
August 1992.
SRI International (Network Information Systems Center), Marine, A.,
S. Kirkpatrick, V. Neou, C. Ward, "INTERNET: Getting Started",
May 1992.
US DOMAIN TEMPLATE [5/93]
Please submit the following two page template to the
(us-domain@isi.edu). Sections or fields of this form marked with an
asterisk (*) may be copied as many times as necessary to complete this
application. PLEASE DO NOT ALTER THIS APPLICATION IN ANY WAY
=====================================================================
1. REGISTRATION TYPE
(N)ew (M)odify (D)elete..:
2.* FULLY-QUALIFIED DOMAIN NAME:
3. ORGANIZATION INFORMATION
3a. Organization Name.....:
3b. Address Line 1........:
3b. Address Line 2........:
3c. City..................:
3d. State.................:
3e. Zip/Code..............:
4. Date Operational......:
5. ADMINISTRATIVE CONTACT
5a. NIChandle (if known)..:
5b. Whole Name............:
5c. Organization Name.....:
5d. Address Line 1........:
5d. Address Line 2........:
5e. City..................:
5f. State.................:
5g. Zip/Code..............:
5h.* Voice Phone...........:
5i.* Electronic Mailbox....:
6. TECHNICAL AND ZONE CONTACT
6a. NIChandle (if known)..:
6b. Whole Name............:
6c. Organization Name.....:
6d. Address Line 1........:
5d. Address Line 2........:
6e. City..................:
6f. State.................:
6g. Zip/Code..............:
6h.* Voice Phone...........:
6i.* Electronic Mailbox....:
7. PRIMARY SERVER: HOSTNAME, NETADDRESS
7a. Hostname.............:
7b.* IP Address...........:
8. * SECONDARY SERVER: HOSTNAME, NETADDRESS
8a.* Hostname.............:
8b.* IP Address...........:
9. DESCRIPTION OF ORG/DOMAIN..:
QUESTIONS FOR NON-DELEGATED HOSTS OR NON-IP HOSTS (such as UUCP)
10. COMMUNICATION MEANS WITH THE INTERNET
(I)P (U)UCP (O)ther...:
10a. Forwarding Host......:
10b. Contact Name.........:
10c. Contact Email........:
11. RESOURCE RECORDS (RRs)
11a. FQ DOMAIN NAME........:
11b.* IP ADDRESS............:
11c. HARDWARE..............:
11d. OPERATING SYS.........:
11e. WKS...................:
11f.* MX....................: